home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS in a Box 7
/
BBS in a Box - Macintosh - Volume VII (BBS in a Box) (January 1993).iso
/
Files
/
Tele
/
U-V
/
Userlog Utils.cpt
/
ListUsers_UL2TXT_TXT2UL Notes
< prev
next >
Wrap
Text File
|
1988-11-07
|
6KB
|
143 lines
ListUsers 3.0, UL2TXT, & TXT2UL Notes
These utilities evolved from my earlier ListUsers utility, which simply
translated the Userlog into sorted text form. ListUsers 3.0 performs the same
function, but also provides the capability to sort the actual Userlog as well
as to clear any or all of the System<n>.MSG flags.
The other utilities perform inverse functions, UL2TXT converting the Userlog
into a tab-delineated text format, and TXT2UL converting a suitably formatted
file back into Userlog form. The primary difference between UL2TXT and
ListUsers is that the former program outputs every piece of information within
the file, including which messages sections are selected for "Read All", which
System.Msg files have been read and terminal options. The output is also much
harder to read from a human perspective. It was written so that I could use
global changes within a text editor, i.e. 'Change all users with a time limit
of 60 and a privilege of 80, to a time limit of 75 and a privilege level of 80'
or 'Add msg base 11 to all users'.
Both ListUsers and UL2TXT output with a file type of QED1, which is that used
by QUED and QUED/M. QUED/M is unquestionably the best text editor available,
and much of the power comes from macro capabilities. For example, I recently
changed my entire menu structure so that all file DL commands with a privilege
level of '>80' were changed into 3 commands at levels =80, =100, and >=120. The
rest of the command, including the file section path was unchanged. The
important thing about this is that I did it as a global change on multiple
sections and I am certain that none were missed, in addition to avoiding a lot
of tedious labor. (This operation was performed by using ListMenus to get a
single text file listing all the menus, editting it, and rebuilding the menus
from the text file, also using ListMenus.) If you run a RRHost BBS, QUED/M is
worth the money!
Details:
ListMenus 3.0
If the Userlog is not in the same folder as ListUsers, then a very brief error
message will be displayed and the program will terminate. Otherwise the
following dialog will occur. Computer prompts are shown in quotes:
' Possible Sort Options: '
' NAME or ACCESS or DLS or ULS or LEVEL or DATE'
'Enter option (<CR> = No Sort) : ' <response>
This answer just tells the program how to sort the output. Case is unimportant,
although the entire would should be entered.
' Possible Output Options: '
' BRIEF, NONE or <CR>'
'Enter option (<CR> = Full output) : '<response>
Once again case is insignificant, but these options can be abbreviated, i.e. a
"b" is as good as "BRIEF". Brief output omits the password, so that output
could be distributed without compromising security. NONE will prevent any text
output. The default if full output including passwords. The output file will
always be "USERLOG.Lst"
' Save modified UserLog?: '
'Y or N (Defaults to Yes) '<response>
Anything other than a 'No' response wil cause ListUsers to rewrite the Userlog
with a sorted copy. If the answer is no, the next question will be skipped
since it doesn't make sense to clear the flags unless one is planning to save
the modified copy.
'Clear System<N>.Msg Read flag?'
'Enter "1" and/or "2" and/or "3" to clear that flag: '<response>
If a "2" is entered, RRHost will mark SYSTEM2.MSG as unread by all users. The
numbers "1" and "3" are handled the same. Any subset may be entered, i.e. "1",
"31", "23" and "12" are all legal.
After all the questions are answered, the Userlog is processed, and USERLOG.LST
is (conditionally) produced.
UL2TXT
The program must be in the same folder as the Userlog. When opened the program
creates a file called UserLog.TXT which can be viewed with any text editor. The
output consists of one line per user. Each line contains:
Privilege level
Time Limit
Number of calls
Number of msgs
Number of Private messages
Number of DLs
Number of ULs
Messages Sections fo Read ALL (see below)
Flags (also see below)
Date & Time of last call.
First Name
Last Name
Password
Location
The message sections which are visible with the Read All command are indicated
with an asterisk in a 20 column record, e.g "***..**.***........." indicates
that this user can read bases 1,2,3,6,7,9,10, and 11, and can not read 4,5, or
8. The first column is always set and can be used as a placeholder for a text
editor. The QUED/M command, if used in a macro,
Change "\(\*.......\)." to "*\1*" " would set all users to read base 8
without changing the other settings.
The flags field is shown in a similar manner. The string, "LXH.2.&", shows
that this user requires a Linefeed after each return, doesn't want any 'screen
feeds', wants 'H' menus, and has read SYSTEM2.MSG, but not SYSTEM1.MSG or
SYSTEM2.MSG. The '&' is just there for text editor change commands. The 'X'
field would be a "." if a FormFeed is to be used for new screens and would be
"C" if 24 carriage returns are to be used.
The other fields are fairly obvious.
TXT2UL
The last program simply takes a 'USERLOG.TXT' file, in the same folder as the
program, and converts it to a Userlog. The flags and msg base fields are
interpreted as noted above. Very little error checking is done, so be careful.
For example, trailing blanks are not stripped, so one could easily change a
user name and not see it. Every field must be separated from the others by a
Tab character. Failure to do so could cause real problems.
Rights and such...
I retain all rights to these programs, but they may be freely used and freely
distributed, as long as this file is included in the distribution package. (I
prefer not to answer questions from people with executables but no docs!) I
encourage users to check out my shareware products, FSP, AnalyzeCL, ListMenus,
and TSX, available on the FreeSoft RT on GEnie.
PS: If anyone wishes to put together a Hypercard stack the reads UL2TXT output
and produces a Userlog stack, they have my encouragement. I'll do one
eventually if no one beats me to it.